Dropping a configured transmission based on transmission power and feedback channel priority

ABSTRACT

A wireless device, receives configuration parameters of: a first resource for a first channel, of a carrier, for transmitting first feedback; and a second resource for a second channel of the carrier for transmitting second feedback. The first resource and the second resource overlap in one or more symbol durations. Power levels are determined comprising: a first power level for transmission of the first feedback via the first resource; and a second power level for transmission of the second feedback via the second resource. In response to a sum of the power levels being larger than an allowed transmission power, a configured transmission of the first feedback via the first resource is dropped. The dropping is based on a first priority of the first channel. The second feedback is transmitted via the second resource.

This application is a continuation of U.S. patent Ser. No. 16/800,524,filed Feb. 25, 2020, which is a continuation of U.S. patent Ser. No.16/142,959, filed Sep. 26, 2018, (now U.S. Pat. No. 10,582,454, issuedon Mar. 3, 2020) which claims the benefit of U.S. ProvisionalApplication No. 62/563,916, filed Sep. 27, 2017, which are herebyincorporated by reference in their entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present invention.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present invention.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention.

FIG. 6 is an example diagram for a protocol structure withmulti-connectivity as per an aspect of an embodiment of the presentinvention.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present invention.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present invention.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentinvention.

FIG. 10A and FIG. 10B are example diagrams for interfaces between a 5Gcore network (e.g. NGC) and base stations (e.g. gNB and eLTE eNB) as peran aspect of an embodiment of the present invention.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RAN(e.g. gNB) and LTE RAN (e.g. (e)LTE eNB) as per an aspect of anembodiment of the present invention.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present invention.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present invention.

FIG. 14 is an example diagram for functional split option examples ofthe centralized gNB deployment scenario as per an aspect of anembodiment of the present invention.

FIG. 15 is an example power scaling process as per an aspect of anembodiment of the present invention.

FIG. 16 is an example power scaling process as per an aspect of anembodiment of the present invention.

FIG. 17 is an example power scaling process as per an aspect of anembodiment of the present invention.

FIG. 18 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable operation of carrieraggregation. Embodiments of the technology disclosed herein may beemployed in the technical field of multicarrier communication systems.More particularly, the embodiments of the technology disclosed hereinmay relate to power control in a multicarrier communication systems.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

CP cyclic prefix

DL downlink

DCI downlink control information

DC dual connectivity

eMBB enhanced mobile broadband

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

mMTC massive machine type communications

NAS non-access stratum

NR new radio

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG resource block groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TTI transmission time intervalTB transport block

UL uplink

UE user equipment

URLLC ultra-reliable low-latency communications

VHDL VHSIC hardware description language

CU central unit

DU distributed unit

Fs-C Fs-control plane

Fs-U Fs-user plane

gNB next generation node B

NGC next generation core

NG CP next generation control plane core

NG-C NG-control plane

NG-U NG-user plane

NR new radio

NR MAC new radio MAC

NR PHY new radio physical

NR PDCP new radio PDCP

NR RLC new radio RLC

NR RRC new radio RRC

NSSAI network slice selection assistance information

PLMN public land mobile network

UPGW user plane gateway

Xn-C Xn-control plane

Xn-U Xn-user plane

Xx-C Xx-control plane

Xx-U Xx-user plane

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention. As illustrated in thisexample, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1 , guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentinvention. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) mayconsist of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. A slot may be 7 or 14 OFDM symbols for the samesubcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDMsymbols for the same subcarrier spacing higher than 60 kHz with normalCP. A slot may contain all downlink, all uplink, or a downlink part andan uplink part and/or alike. Slot aggregation may be supported, e.g.,data transmission may be scheduled to span one or multiple slots. In anexample, a mini-slot may start at an OFDM symbol in a subframe. Amini-slot may have a duration of one or more OFDM symbols. Slot(s) mayinclude a plurality of OFDM symbols 203. The number of OFDM symbols 203in a slot 206 may depend on the cyclic prefix length and subcarrierspacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3 . The quantity ofdownlink subcarriers or RBs may depend, at least in part, on thedownlink transmission bandwidth 306 configured in the cell. The smallestradio resource unit may be called a resource element (e.g. 301).Resource elements may be grouped into resource blocks (e.g. 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g. 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. In an illustrative example, a resource block may correspondto one slot in the time domain and 180 kHz in the frequency domain (for15 KHz subcarrier bandwidth and 12 subcarriers).

In an example embodiment, multiple numerologies may be supported. In anexample, a numerology may be derived by scaling a basic subcarrierspacing by an integer N. In an example, scalable numerology may allow atleast from 15 kHz to 480 kHz subcarrier spacing. The numerology with 15kHz and scaled numerology with different subcarrier spacing with thesame CP overhead may align at a symbol boundary every 1 ms in a NRcarrier.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention. FIG. 5A shows an example uplink physical channel.The baseband signal representing the physical uplink shared channel mayperform the following processes. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments. The functions may comprise scrambling,modulation of scrambled bits to generate complex-valued symbols, mappingof the complex-valued modulation symbols onto one or severaltransmission layers, transform precoding to generate complex-valuedsymbols, precoding of the complex-valued symbols, mapping of precodedcomplex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present invention.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1 ,FIG. 2 , FIG. 3 , FIG. 5 , and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, a 5G networkmay include a multitude of base stations, providing a user plane NRPDCP/NR RLC/NR MAC/NR PHY and control plane (NR RRC) protocolterminations towards the wireless device. The base station(s) may beinterconnected with other base station(s) (e.g. employing an Xninterface). The base stations may also be connected employing, forexample, an NG interface to an NGC. FIG. 10A and FIG. 10B are examplediagrams for interfaces between a 5G core network (e.g. NGC) and basestations (e.g. gNB and eLTE eNB) as per an aspect of an embodiment ofthe present invention. For example, the base stations may beinterconnected to the NGC control plane (e.g. NG CP) employing the NG-Cinterface and to the NGC user plane (e.g. UPGW) employing the NG-Uinterface. The NG interface may support a many-to-many relation between5G core networks and base stations.

A base station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink, itmay be the Uplink Primary Component Carrier (UL PCC). Depending onwireless device capabilities, Secondary Cells (SCells) may be configuredto form together with the PCell a set of serving cells. In the downlink,the carrier corresponding to an SCell may be a Downlink SecondaryComponent Carrier (DL SCC), while in the uplink, it may be an UplinkSecondary Component Carrier (UL SCC). An SCell may or may not have anuplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTE or5G technology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand multi-connectivity as per an aspect of an embodiment of the presentinvention. NR may support multi-connectivity operation whereby amultiple RX/TX UE in RRC_CONNECTED may be configured to utilize radioresources provided by multiple schedulers located in multiple gNBsconnected via a non-ideal or ideal backhaul over the Xn interface. gNBsinvolved in multi-connectivity for a certain UE may assume two differentroles: a gNB may either act as a master gNB or as a secondary gNB. Inmulti-connectivity, a UE may be connected to one master gNB and one ormore secondary gNBs. FIG. 7 illustrates one example structure for the UEside MAC entities when a Master Cell Group (MCG) and a Secondary CellGroup (SCG) are configured, and it may not restrict implementation.Media Broadcast Multicast Service (MBMS) reception is not shown in thisfigure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. Three alternativesmay exist, an MCG bearer, an SCG bearer and a split bearer as shown inFIG. 6 . NR RRC may be located in master gNB and SRBs may be configuredas a MCG bearer type and may use the radio resources of the master gNB.Multi-connectivity may also be described as having at least one bearerconfigured to use radio resources provided by the secondary gNB.Multi-connectivity may or may not be configured/implemented in exampleembodiments of the invention.

In the case of multi-connectivity, the UE may be configured withmultiple NR MAC entities: one NR MAC entity for master gNB, and other NRMAC entities for secondary gNBs. In multi-connectivity, the configuredset of serving cells for a UE may comprise of two subsets: the MasterCell Group (MCG) containing the serving cells of the master gNB, and theSecondary Cell Groups (SCGs) containing the serving cells of thesecondary gNBs. For a SCG, one or more of the following may be applied:at least one cell in the SCG has a configured UL CC and one of them,named PSCell (or PCell of SCG, or sometimes called PCell), is configuredwith PUCCH resources; when the SCG is configured, there may be at leastone SCG bearer or one Split bearer; upon detection of a physical layerproblem or a random access problem on a PSCell, or the maximum number ofNR RLC retransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG are stopped, amaster gNB may be informed by the UE of a SCG failure type, for splitbearer, the DL data transfer over the master gNB is maintained; the NRRLC AM bearer may be configured for the split bearer; like PCell, PSCellmay not be de-activated; PSCell may be changed with a SCG change (e.g.with security key change and a RACH procedure); and/or a direct bearertype change between a Split bearer and a SCG bearer or simultaneousconfiguration of a SCG and a Split bearer may or may not supported.

With respect to the interaction between a master gNB and secondary gNBsfor multi-connectivity, one or more of the following principles may beapplied: the master gNB may maintain the RRM measurement configurationof the UE and may, (e.g, based on received measurement reports ortraffic conditions or bearer types), decide to ask a secondary gNB toprovide additional resources (serving cells) for a UE; upon receiving arequest from the master gNB, a secondary gNB may create a container thatmay result in the configuration of additional serving cells for the UE(or decide that it has no resource available to do so); for UEcapability coordination, the master gNB may provide (part of) the ASconfiguration and the UE capabilities to the secondary gNB; the mastergNB and the secondary gNB may exchange information about a UEconfiguration by employing of NR RRC containers (inter-node messages)carried in Xn messages; the secondary gNB may initiate a reconfigurationof its existing serving cells (e.g., PUCCH towards the secondary gNB);the secondary gNB may decide which cell is the PSCell within the SCG;the master gNB may or may not change the content of the NR RRCconfiguration provided by the secondary gNB; in the case of a SCGaddition and a SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s); both a master gNB and secondarygNBs may know the SFN and subframe offset of each other by OAM, (e.g.,for the purpose of DRX alignment and identification of a measurementgap). In an example, when adding a new SCG SCell, dedicated NR RRCsignaling may be used for sending required system information of thecell as for CA, except for the SFN acquired from a MIB of the PSCell ofa SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present invention. In Example 1, pTAG comprises PCell,and an sTAG comprises SCell1. In Example 2, a pTAG comprises a PCell andSCell1, and an sTAG comprises SCell2 and SCell3. In Example 3, pTAGcomprises PCell and SCell1, and an sTAG1 includes SCell2 and SCell3, andsTAG2 comprises SCell4. Up to four TAGs may be supported in a cell group(MCG or SCG) and other example TAG configurations may also be provided.In various examples in this disclosure, example mechanisms are describedfor a pTAG and an sTAG. Some of the example mechanisms may be applied toconfigurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentinvention. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timingalignment may be achieved through a random access procedure. This mayinvolve a UE transmitting a random access preamble and an eNB respondingwith an initial TA command NTA (amount of timing advance) within arandom access response window. The start of the random access preamblemay be aligned with the start of a corresponding uplink subframe at theUE assuming NTA=0. The eNB may estimate the uplink timing from therandom access preamble transmitted by the UE. The TA command may bederived by the eNB based on the estimation of the difference between thedesired UL timing and the actual UL timing. The UE may determine theinitial uplink transmission timing relative to the correspondingdownlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to some of thevarious aspects of embodiments, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding (configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, for example, at least one RRC reconfigurationmessage, may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of the pTAG(when an SCell is added/configured without a TAG index, the SCell may beexplicitly assigned to the pTAG). The PCell may not change its TA groupand may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the UE mayperform an SCell release. If the received RRC Connection Reconfigurationmessage includes the sCellToAddModList, the UE may perform SCelladditions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on thePCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase.

Accommodating the PUCCH transmissions on the PCell may lead to a highPUCCH load on the PCell. A PUCCH on an SCell may be introduced tooffload the PUCCH resource from the PCell. More than one PUCCH may beconfigured for example, a PUCCH on a PCell and another PUCCH on anSCell. In the example embodiments, one, two or more cells may beconfigured with PUCCH resources for transmitting CSI/ACK/NACK to a basestation. Cells may be grouped into multiple PUCCH groups, and one ormore cell within a group may be configured with a PUCCH. In an exampleconfiguration, one SCell may belong to one PUCCH group. SCells with aconfigured PUCCH transmitted to a base station may be called a PUCCHSCell, and a cell group with a common PUCCH resource transmitted to thesame base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/orif theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the invention may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RANand LTE RAN as per an aspect of an embodiment of the present invention.The tight interworking may enable a multiple RX/TX UE in RRC_CONNECTEDto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g. (e)LTE eNB and gNB) connected via anon-ideal or ideal backhaul over the Xx interface between LTE eNB andgNB or the Xn interface between eLTE eNB and gNB. Base stations involvedin tight interworking for a certain UE may assume two different roles: abase station may either act as a master base station or as a secondarybase station. In tight interworking, a UE may be connected to one masterbase station and one secondary base station. Mechanisms implemented intight interworking may be extended to cover more than two base stations.

In FIG. 11A and FIG. 11B, a master base station may be an LTE eNB, whichmay be connected to EPC nodes (e.g. to an MME via the S 1-C interfaceand to an S-GW via the S1-U interface), and a secondary base station maybe a gNB, which may be a non-standalone node having a control planeconnection via an Xx-C interface to an LTE eNB. In the tightinterworking architecture of FIG. 11A, a user plane for a gNB may beconnected to an S-GW through an LTE eNB via an Xx-U interface betweenLTE eNB and gNB and an S1-U interface between LTE eNB and S-GW. In thearchitecture of FIG. 11B, a user plane for a gNB may be connecteddirectly to an S-GW via an S1-U interface between gNB and S-GW.

In FIG. 11C and FIG. 11D, a master base station may be a gNB, which maybe connected to NGC nodes (e.g. to a control plane core node via theNG-C interface and to a user plane core node via the NG-U interface),and a secondary base station may be an eLTE eNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to a gNB. In the tight interworking architecture of FIG. 11C,a user plane for an eLTE eNB may be connected to a user plane core nodethrough a gNB via an Xn-U interface between eLTE eNB and gNB and an NG-Uinterface between gNB and user plane core node. In the architecture ofFIG. 11D, a user plane for an eLTE eNB may be connected directly to auser plane core node via an NG-U interface between eLTE eNB and userplane core node.

In FIG. 11E and FIG. 11F, a master base station may be an eLTE eNB,which may be connected to NGC nodes (e.g. to a control plane core nodevia the NG-C interface and to a user plane core node via the NG-Uinterface), and a secondary base station may be a gNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to an eLTE eNB. In the tight interworking architecture of FIG.11E, a user plane for a gNB may be connected to a user plane core nodethrough an eLTE eNB via an Xn-U interface between eLTE eNB and gNB andan NG-U interface between eLTE eNB and user plane core node. In thearchitecture of FIG. 11F, a user plane for a gNB may be connecteddirectly to a user plane core node via an NG-U interface between gNB anduser plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present invention. In FIG. 12A, an LTE eNB may be amaster base station, and a gNB may be a secondary base station. In FIG.12B, a gNB may be a master base station, and an eLTE eNB may be asecondary base station. In FIG. 12C, an eLTE eNB may be a master basestation, and a gNB may be a secondary base station. In 5G network, theradio protocol architecture that a particular bearer uses may depend onhow the bearer is setup. Three alternatives may exist, an MCG bearer, anSCG bearer, and a split bearer as shown in FIG. 12A, FIG. 12B, and FIG.12C. NR RRC may be located in master base station, and SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster base station. Tight interworking may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Tight interworking may or may not beconfigured/implemented in example embodiments of the invention.

In the case of tight interworking, the UE may be configured with two MACentities: one MAC entity for master base station, and one MAC entity forsecondary base station. In tight interworking, the configured set ofserving cells for a UE may comprise of two subsets: the Master CellGroup (MCG) containing the serving cells of the master base station, andthe Secondary Cell Group (SCG) containing the serving cells of thesecondary base station. For a SCG, one or more of the following may beapplied: at least one cell in the SCG has a configured UL CC and one ofthem, named PSCell (or PCell of SCG, or sometimes called PCell), isconfigured with PUCCH resources; when the SCG is configured, there maybe at least one SCG bearer or one split bearer; upon detection of aphysical layer problem or a random access problem on a PSCell, or themaximum number of (NR) RLC retransmissions has been reached associatedwith the SCG, or upon detection of an access problem on a PSCell duringa SCG addition or a SCG change: a RRC connection re-establishmentprocedure may not be triggered, UL transmissions towards cells of theSCG are stopped, a master base station may be informed by the UE of aSCG failure type, for split bearer, the DL data transfer over the masterbase station is maintained; the RLC AM bearer may be configured for thesplit bearer; like PCell, PSCell may not be de-activated; PSCell may bechanged with a SCG change (e.g. with security key change and a RACHprocedure); and/or neither a direct bearer type change between a Splitbearer and a SCG bearer nor simultaneous configuration of a SCG and aSplit bearer are supported.

With respect to the interaction between a master base station and asecondary base station, one or more of the following principles may beapplied: the master base station may maintain the RRM measurementconfiguration of the UE and may, (e.g, based on received measurementreports, traffic conditions, or bearer types), decide to ask a secondarybase station to provide additional resources (serving cells) for a UE;upon receiving a request from the master base station, a secondary basestation may create a container that may result in the configuration ofadditional serving cells for the UE (or decide that it has no resourceavailable to do so); for UE capability coordination, the master basestation may provide (part of) the AS configuration and the UEcapabilities to the secondary base station; the master base station andthe secondary base station may exchange information about a UEconfiguration by employing of RRC containers (inter-node messages)carried in Xn or Xx messages; the secondary base station may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary base station); the secondary base station may decide whichcell is the PSCell within the SCG; the master base station may notchange the content of the RRC configuration provided by the secondarybase station; in the case of a SCG addition and a SCG SCell addition,the master base station may provide the latest measurement results forthe SCG cell(s); both a master base station and a secondary base stationmay know the SFN and subframe offset of each other by OAM, (e.g., forthe purpose of DRX alignment and identification of a measurement gap).In an example, when adding a new SCG SCell, dedicated RRC signaling maybe used for sending required system information of the cell as for CA,except for the SFN acquired from a MIB of the PSCell of a SCG.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present invention. In thenon-centralized deployment scenario in FIG. 13A, the full protocol stack(e.g. NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported atone node. In the centralized deployment scenario in FIG. 13B, upperlayers of gNB may be located in a Central Unit (CU), and lower layers ofgNB may be located in Distributed Units (DU). The CU-DU interface (e.g.Fs interface) connecting CU and DU may be ideal or non-ideal. Fs-C mayprovide a control plane connection over Fs interface, and Fs-U mayprovide a user plane connection over Fs interface. In the centralizeddeployment, different functional split options between CU and DUs may bepossible by locating different protocol layers (RAN functions) in CU andDU. The functional split may support flexibility to move RAN functionsbetween CU and DU depending on service requirements and/or networkenvironments. The functional split option may change during operationafter Fs interface setup procedure, or may change only in Fs setupprocedure (i.e. static during operation after Fs setup procedure).

FIG. 14 is an example diagram for different functional split optionexamples of the centralized gNB deployment scenario as per an aspect ofan embodiment of the present invention. In the split option example 1,an NR RRC may be in CU, and NR PDCP, NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 2, an NR RRC and NR PDCP may be inCU, and NR RLC, NR MAC, NR PHY, and RF may be in DU. In the split optionexample 3, an NR RRC, NR PDCP, and partial function of NR RLC may be inCU, and the other partial function of NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 4, an NR RRC, NR PDCP, and NR RLCmay be in CU, and NR MAC, NR PHY, and RF may be in DU. In the splitoption example 5, an NR RRC, NR PDCP, NR RLC, and partial function of NRMAC may be in CU, and the other partial function of NR MAC, NR PHY, andRF may be in DU. In the split option example 6, an NR RRC, NR PDCP, NRRLC, and NR MAC may be in CU, and NR PHY and RF may be in DU. In thesplit option example 7, an NR RRC, NR PDCP, NR RLC, NR MAC, and partialfunction of NR PHY may be in CU, and the other partial function of NRPHY and RF may be in DU. In the split option example 8, an NR RRC, NRPDCP, NR RLC, NR MAC, and NR PHY may be in CU, and RF may be in DU.

The functional split may be configured per CU, per DU, per UE, perbearer, per slice, or with other granularities. In per CU split, a CUmay have a fixed split, and DUs may be configured to match the splitoption of CU. In per DU split, each DU may be configured with adifferent split, and a CU may provide different split options fordifferent DUs. In per UE split, a gNB (CU and DU) may provide differentsplit options for different UEs. In per bearer split, different splitoptions may be utilized for different bearer types. In per slice splice,different split options may be applied for different slices.

In an example embodiment, the new radio access network (new RAN) maysupport different network slices, which may allow differentiatedtreatment customized to support different service requirements with endto end scope. The new RAN may provide a differentiated handling oftraffic for different network slices that may be pre-configured, and mayallow a single RAN node to support multiple slices. The new RAN maysupport selection of a RAN part for a given network slice, by one ormore slice ID(s) or NSSAI(s) provided by a UE or a NGC (e.g. NG CP). Theslice ID(s) or NSSAI(s) may identify one or more of pre-configurednetwork slices in a PLMN. For initial attach, a UE may provide a sliceID and/or an NSSAI, and a RAN node (e.g. gNB) may use the slice ID orthe NSSAI for routing an initial NAS signaling to an NGC control planefunction (e.g. NG CP). If a UE does not provide any slice ID or NSSAI, aRAN node may send a NAS signaling to a default NGC control planefunction. For subsequent accesses, the UE may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. The RAN resource isolation may be achieved by avoidingthat shortage of shared resources in one slice breaks a service levelagreement for another slice.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. Thisrequires not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum is therefore needed for cellularoperators to meet the increasing demand. Considering user expectationsof high data rates along with seamless mobility, it is beneficial thatmore spectrum be made available for deploying macro cells as well assmall cells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, can be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA offers an alternative for operators to make use of unlicensedspectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAutilizes at least energy detection to determine the presence or absenceof other signals on a channel in order to determine if a channel isoccupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission. Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by UEs; time & frequency synchronizationof UEs.

In an example embodiment, DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the eNBtransmissions can start only at the subframe boundary. LAA may supporttransmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

LBT procedure may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than this threshold, the node assumes that thechannel is not free. While nodes may follow such regulatoryrequirements, a node may optionally use a lower threshold for energydetection than that specified by regulatory requirements. In an example,LAA may employ a mechanism to adaptively change the energy detectionthreshold, e.g., LAA may employ a mechanism to adaptively lower theenergy detection threshold from an upper bound. Adaptation mechanism maynot preclude static or semi-static setting of the threshold. In anexample Category 4 LBT mechanism or other type of LBT mechanisms may beimplemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (e.g. LBT without randomback-off) may be implemented. The duration of time that the channel issensed to be idle before the transmitting entity transmits may bedeterministic. In an example, Category 3 (e.g. LBT with random back-offwith a contention window of fixed size) may be implemented. The LBTprocedure may have the following procedure as one of its components. Thetransmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by theminimum and maximum value of N. The size of the contention window may befixed. The random number N may be employed in the LBT procedure todetermine the duration of time that the channel is sensed to be idlebefore the transmitting entity transmits on the channel. In an example,Category 4 (e.g. LBT with random back-off with a contention window ofvariable size) may be implemented. The transmitting entity may draw arandom number N within a contention window. The size of contentionwindow may be specified by the minimum and maximum value of N. Thetransmitting entity may vary the size of the contention window whendrawing the random number N. The random number N is used in the LBTprocedure to determine the duration of time that the channel is sensedto be idle before the transmitting entity transmits on the channel.

LAA may employ uplink LBT at the UE. The UL LBT scheme may be differentfrom the DL LBT scheme (e.g. by using different LBT mechanisms orparameters) for example, since the LAA UL is based on scheduled accesswhich affects a UE's channel contention opportunities. Otherconsiderations motivating a different UL LBT scheme include, but are notlimited to, multiplexing of multiple UEs in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. An UL transmission burst from aUE perspective may be a continuous transmission from a UE with notransmission immediately before or after from the same UE on the sameCC. In an example, UL transmission burst is defined from a UEperspective. In an example, an UL transmission burst may be defined froman eNB perspective. In an example, in case of an eNB operating DL+UL LAAover the same unlicensed carrier, DL transmission burst(s) and ULtransmission burst(s) on LAA may be scheduled in a TDM manner over thesame unlicensed carrier. For example, an instant in time may be part ofa DL transmission burst or an UL transmission burst.

In an example, a wireless device may receive one or more messagescomprising one or more radio resource configuration (RRC) messages fromone or more base stations (e.g., one or more NR gNBs and/or one or moreLTE eNBs and/or one or more eLTE eNBs, etc.). In an example, the one ormore messages may comprise configuration parameters for a plurality oflogical channels. In an example, the one one or messages may comprise alogical channel identifier for each of the plurality of logicalchannels. In an example, the logical channel identifier may be one of aplurality of logical channel identifiers. In an example, the pluralityof logical channel identifiers may be pre-configured. In an example, thelogical channel identifier may be one of a plurality of consecutiveintegers.

In an example, the plurality of logical channels configured for awireless device may correspond to one or more bearers. In an example,there may be one-to-one mapping/correspondence between a bearer and alogical channel. In an example, there may be one-to-manymapping/correspondence between one or more bearers and one or morelogical channels. In an example, a bearer may be mapped to a pluralityof logical channels. In an example, data from a packet data convergenceprotocol (PDCP) entity corresponding to a bearer may be duplicated andmapped to a plurality of radio link control (RLC) entities and/orlogical channels. In an example, scheduling of the plurality of logicalchannels may be performed by a single medium access control (MAC)entity. In an example, scheduling of the plurality of logical channelsmay be performed by a two or more MAC entities. In an example, a logicalchannel may be scheduled by one of a plurality of MAC entities. In anexample, the one or more beares may comprise one or more data radiobearers. In an example, the one or more bearers may comprise one or moresignaling radio bearers. In an example, the one or more bearers maycorrespond to one or more application and/or quality of service (QoS)requirements. In an example, one or more bearers may correspond to ultrareliable low latency communications (URLLC) applications and/or enhancedmobile broadband (eMBB) applications and/or massive machine to machinecommunications (mMTC) applications.

In an example, a first logical channel of the plurality of logicalchannels may be mapped to one or more of a plurality of transmissiontime intervals (TTIs)/numerologies. In an example, a logical channel maynot be mapped to one or more of the plurality of TTIs/numerologies. Inan example, a logical channel corresponding to a URLLC bearer may bemapped to one or more first TTIs and a logical corresponding to an eMBBapplication may be mapped to one or more second TTIs, wherein the one ormore first TTIs may have shorter duration than the one or more secondTTIs. In an example, the plurality of TTIs/numerologies may bepre-configured at the wireless device. In an example, the one or moremessages may comprise the configuration parameters of the plurality ofTTIs/numerologies. In an example, a base station may transmit agrant/DCI to a wireless device, wherein the grant/DCI may compriseindication of a cell and/or a TTI/numerology that the wireless devicemay transmit data. In an example, a first field in the grant/DCI mayindicate the cell and a second field in the grant/DCI may indicate theTTI/numerology. In an example, a field in the grant/DCI may indicateboth the cell and the TTI/numerology.

In an example, the one or more messages may comprise a logical channelgroup identifier for one or more of the plurality of the logicalchannels. In an example, one or more of the plurality of logicalchannels may be assigned a logical channel group identifier n, 0≤n≤NT(e.g., N=3, or 5, or 7, or 11 or 15, etc.). In an example, the one ormore of the plurality of logical channels with the logical channel groupidentifier may be mapped to a same one or more TTIs/numerologies. In anexample, the one or more of the plurality of logical channels with thelogical channel group identifier may only be mapped to a same one ormore TTIs/numerologies. In an example, the one more of the plurality oflogical channels may correspond to a same application and/or QoSrequirements. In an example, a first one or more logical channels may beassigned logical channel identifier(s) and logical channel groupidentifier(s) and a second one or more logical channels may be assignedlogical channel identifier(s). In an example, a logical channel groupmay comprise of one logical channel.

In an example, the one or more messages may comprise one or more firstfields indicating mapping between the plurality of logical channels andthe plurality of TTIs/numerologies and/or cells. In an example, the oneor more first fields may comprise a first value indicating a logicalchannel is mapped to one or more first TTI duration shorter than orequal to the first value. In an example, the one or more first fieldsmay comprise a second value indicating a logical channel is mapped toone or more second TTI durations longer than or equal to the secondvalue. In an example, the one or more first fields may comprise and/orindicate one or more TTIs/numerologies and/or cells that a logicalchannel is mapped to. In an example, the mapping may be indicated usingone or more bitmaps. In an example, if a value of 1 in a bitmapassociated with a logical channel may indicate that the logical channelis mapped to a corresponding TTI/numerology and/or cell. In an example,if a value of 0 in the bitmap associated with a logical channel mayindicate that the logical channel is not mapped to a correspondingTTI/numerology and/or cell. In an example, the one or more messages maycomprise configuration parameters for the plurality of the logicalchannels. In an example, the configuration parameters for a logicalchannel may comprise an associated bitmap for the logical channelwherein the bitmap may indicate the mapping between the logical channeland the plurality of TTIs/numerologie and/or cells.

In an example, a first logical channel may be assigned at least a firstlogical channel priority. In an example, the first logical channel maybe assigned one or more logical channel priorities for one or moreTTIs/numerologies. In an example, the first logical channel may beassigned a logical channel priority for each of the plurality ofTTIs/numerologies. In an example, a logical channel may be assigned alogical channel priority for each of one or more of the plurality ofTTIs/numerologies. In an example, a logical channel may be assigned alogical channel priority for each of one or more TTIs/numerologieswherein the logical channel is mapped to the each of the one or moreTTIs/numerologies. In an example, the one or more messages may compriseone or more second fields indicating priorities of a logical channel onone or more TTIs/numerologies. In an example, the one or more secondfields may comprise one or more sequences indicating priorities of alogical channel on one or more TTIs/numerologies. In an example, the oneor more second fields may comprise a plurality of sequences for theplurality of logical channels. A sequence corresponding to a logicalchannel may indicate the priorities of the logical channel on theplurality of TTIs/numerologies/cells or one or more of the plurality ofTTIs/numerologies/cells. In an example, the priorities may indicatemapping between a logical channel and one or more TTIs/numerologies. Inan example, a priority of a logical channel with a given value (e.g.,zero or minus infinity or a negative value) for a TTI/numerology mayindicate that the logical channel is not mapped to the TTI/numerology.In an example, sizes of the sequence may be variable. In an example, asize of a sequence associated with a logical channel may be a number ofTTIs/numerologies to which the logical channel is mapped. In an example,the sizes of the sequence may be fixed, e.g., the number ofTTIs/numerologies/cells.

In an example, a TTI/numerology for a grant (e.g., as indicated by thegrant/DCI) may not accept data from one or more logical channels. In anexample, the one or more logical channels may not be mapped to theTTI/numerology indicated in the grant. In an example, a logical channelof the one or more logical channels may be configured to be mapped toone or more TTIs/numerologies and the TTI/numerology for the grant maynot be among the one or more TTIs/numerologies. In an example, a logicalchannel of the one or more logical channels may be configured with amax-TTI parameter indicating that the logical channel may not be mappedto a TTI longer than max-TTI, and the grant may be for a TTI longer thanmax-TTI. In an example, a logical channel may be configured with amin-TTI parameter indicating that the logical channel may not be mappedto a TTI shorter than min-TTI, and the grant may be for a TTI shorterthan min-TTI. In an example, a logical channel may not be allowed to betransmitted on a cell and/or one or more numerologies and/or one or morenumerologies of a cell. In an example, a logical channel may containduplicate data and the logical channel may be restricted so that thelogical channel is not mapped to a cell/numerology. In an example, thelogical channel may not be configured with an upper layer configurationparameter laa-allowed and the cell may be an LAA cell.

In an example, a MAC entity and/or a multiplexing and assembly entity ofa MAC entity may perform a logical channel prioritization (LCP)procedure to allocate resources of one or more grants, indicated to awireless device by a base station using one or more DCIs, to one or morelogical channel. In an example, the timing between a grant/DCI receptiontime at the wireless device and transmission time may be dynamicallyindicated to the wireless device (e.g., at least using a parameter inthe grant/DCI). In an example, timing between a grant/DCI reception timeat the wireless device and transmission time may be fixed/preconfiguredand/or semi-statically configured. In an example, the LCP procedure forNR may consider the mapping of a logical channel to one or morenumerologies/TTIs, priorities of a logical channel on the one or morenumerologies/TTIs, the numerology/TTI indicated in a grant, etc. The LCPprocedure may multiplex data from one or more logical channels to form aMAC PDU. The amount of data from a logical channel included in a MAC PDUmay depend on the QoS parameters of a bearer and/or service associatedwith the logical channel, priority of the logical channel on thenumerology/TTI indicated in the grant, etc. In an example, one or moregrants may be processed jointly at a wireless device (e.g., resources ofthe one or more grants are allocated substantially at a same time). Inan example, one or more first grants of the one or more grants may begrouped into a grouped grant with capacity equal to sum of thecapacities of the one or more first grants and the resources of thegrouped grant may be allocated to one or more logical channels.

In an example, the MAC layer may provide data transfer services onlogical channel. In an example, different logical channel types may bedefined/configured for different kinds of data transfer services. In anexample, a logical channel type may be defined by what type ofinformation is transferred. In an example, the wireless device mayperform a logical channel prioritization procedure (LCP) when a newtransmission is performed. The LCP may determine the logical channelsmultiplexed in a transport block. A logical channel may be associatedwith buffers at the RLC layer and/or PDCP layer, etc.

In an example, an IE (e.g., LogicalChannelConfig) may be used toconfigure the logical channel parameters. An example,LogicalChannelConfig IE may be as follows:

LogicalChannelConfig ::=   SEQUENCE {  ul-SpecificParameters   SEQUENCE{   priority        INTEGER (1..16),   prioritisedBitRate     ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128,kBps256,infinity, kBps512- v1020, kBps1024-v1020,kBps2048-v1020, spare5, spare4,spare3, spare2,spare1},   bucketSizeDuration     ENUMERATED {ms50,ms100, ms150, ms300, ms500, ms1000, spare2,spare1},  logicalChannelGroup     INTEGER (0..3)  OPTIONAL   -- Need OR  } OPTIONAL, Cond UL  ...,  [[ logicalChannelSR-Mask-r9   ENUMERATED{setup}  OPTIONAL  -- Cond SRmask  ]],  [[logicalChannelSR-Prohibit-r12 BOOLEAN    OPTIONAL   -- Need ON  ]],  [[laa-Allowed-r14    BOOLEAN    OPTIONAL,  -- Need ON  bitRateQueryProhibitTimer-r14 ENUMERATED {s0, s0dot4, s0dot8, s1dot6,s3, s6, s12,s30}    OPTIONAL   --Need OR  ]] }

In an example, bitRateQueryProhibitTimer may be used for bit raterecommendation query in seconds. In an example, bucketSieDuration may beused for logical channel prioritization. In an example, laa-Allowed mayindicate whether the data of a logical channel is allowed to betransmitted via UL of LAA SCells. Value TRUE may indicate that thelogical channel is allowed to be sent via UL of LAA SCells. Value FALSEmay indicate that the logical channel is not allowed to be sent via ULof LAA SCells. In an example, logicalChannelGroup may indicate mappingof logical channel to logical channel group for BSR resporting. In anexample, logicalChannelSR-Mask may control SR triggering on a logicalchannel basis when an uplink grant is configured. In an example, valueTRUE for logicalChannelSR-Prohibit may indicate that thelogicalChannelSR-ProhibitTimer is enabled for the logical channel. In anexample, logicalChannelSR-Prohibit may be configured iflogicalChannelSR-Prohibit is configured. In an example,prioritisedBitRate may indicate Prioritized bit rate for logical channelprioritisation. In an example, priority may indicate priority forlogical channel prioritization procedure.

In an example, for one-symbol short-PUCCH for UCI of up to 2 bits, thesequence length of 12 REs with consecutive mapping within a PRB may beused. In an example, the sequence length may be 24 or 48 Res. In anexample, multiplexing may be used between sequence-based short-PUCCH andother sequences using CDM or FDM (e.g., DMRS for PUSCH/PUCCH, SRS,long-PUCCH). In an example, for the sequence length of 12 REs, thesupported number of base sequences may be 30. The number of cyclicshifts available for one base sequence may be 12. In an example, forone-symbol short-PUCCH for UCI of more than 2 bits, the number of PRBsthat may be used for a PUCCH may be configurable. In an example,contiguous and non-contiguous PRB allocation may be supported. In anexample, contiguous PRB allocation may be prioritized. In an example,the number of DM-RS REs per PRB may be 4. In an example, DM-RS REs maybe at the fixed positions within a PRB. The sequences used for DM-RS maybe PN sequences as for PUSCH. In an example, for one-symbol short-PUCCHfor UCI of more than 2 bits, DMRS REs may be evenly distributed within aPRB. In an example, for 2-symbol short-PUCCH for UCI of more than 2bits, encoded UCI bits may be mapped across two symbols. In an example,one symbol short-PUCCH for UCI of more than 2 bits may be repeatedacross 2 symbols with or without frequency hopping. In an example, for along-PUCCH for UCI of up to 2 bits, DMRS may occur in every other symbolin the long PUCCH (e.g., in even or odd symbols). In an example, for along-PUCCH, frequency-hopping may be enabled/disabled by RRC signaling.In an example, frequency-hopping may be enabled for a long-PUCCH withlarger than a certain duration. In an example, frequency-hopping for aPUCCH may occur within the active UL BWP for the UE. The active BWP mayrefer to BWP associated with the numerology of PUCCH. In an example,long-PUCCH for moderate UCI payload with multiplexing capacity may besupported. In an example, operation of a long PUCCH with more than 2bits UCI may support multiplexing of multiple users on a single PRB. Inan example, for the format of long PUCCH supporting multiplexing ofusers on a single PRB, user multiplexing may be realized by time-domainOCC. In an example, user multiplexing is realized by pre-DFT-OCC. In anexample, user multiplexing may be realized by FDM within the PRB. In anexample, user multiplexing may be realized by pure TDM in the slot. Inan example, for a PUCCH format for UCI with large payload with nomultiplexing capacity within a slot, if frequency-hopping is enabled,for each frequency-hop with less than X symbols, there may be one DMRSsymbol. In an example, X is not smaller than 4. In an example, for eachfrequency-hop with equal to or more than X symbols, there may be twoDMRS symbols. In an example, for each frequency-hop, at least one DMRSsymbol may be included. In an example, for the format of long PUCCHsupporting multiplexing of users, user multiplexing may be realized bytime-domain OCC. In an example, user multiplexing may be realized bypre-DFT-OCC. In an example, user multiplexing may be realized by FDMwithin the PRB. In an example, user multiplexing may be realized by pureTDM in the slot. In an example, to identify PUCCH resource, PUCCHformat, starting symbol in a slot, which slot(s) the PUCCH istransmitted, PRB allocation Code/sequence index(es), frequency hoppingpattern, duration of long PUCCH within a slot, etc. may be known by thewireless device.

In an example, for simultaneous transmission of 2-bit HARQ-ACK and SR,short PUCCH for UCI of up to 2 bits may be used. In an example, forshort PUCCH with UCI of up to 2 bits (e.g., with/without SR) a sequenceselection option may be used. In an example, the same set of sequencesmay be used in short PUCCH and long PUCCH when each is used fortransmission of up to 2 UCI bits on one PRB. In an example, differentset of sequences may be used in short PUCCH and long PUCCH when each isused for transmission of up to 2 UCI bits on one PRB. In an example, forone-symbol short-PUCCH for UCI of more than 2 bits, DMRS Res are evenlydistributed within a PRB. In an example, for short-PUCCH for UCI of morethan 2 bits, DMRS may be mapped on #1, #4, #7, #10 REs for a given RB.The RE indexing may start from 0. In an example, PN sequences as forPUSCH may be used for DMRS sequence of short-PUCCH for UCI of more than2 bits. In an example, for two-symbol PUCCH with more than two UCI bits,the DM-RS density and pattern (e.g., the DM-RS locations) of one-symbolPUCCH with UCI more than two bits may be used for each symbol of the2-symbol PUCCH. In an example, for two-symbol dhort PUCCH with up to twoUCI bits, sequence hopping between the two symbol may be supported. Inan example, for one or two-symbol short PUCCH for UCI of more than twobits, the encoded bits may be scrambled. In an example, for long PUCCHfor UCI of up to two bits, DMRS may be located in even symbols, wherethe symbol may be indexed from the start of the long PUCCH of value 0.In an example, for long PUCCH for UCI up to 2 bits, up to 3 OCCmultiplexing capacity may be supported with frequency hopping. In anexample, for long PUCCH moderate payload size without multiplexingcapability, an additional DMRS symbol in each frequency-hop may beconfigured. In an example, for long PUCCH moderate payload size withoutmultiplexing capability, fixed number of DMRS symbol in eachfrequency-hop (e.g., 1 DMRS symbol) may be used. In an example, for eachfrequency-hop with less than X symbols, there may be one DMRS symbol ineach frequency-hop. In an example, for each frequency-hop with equal toor more than X symbols, there may be two DMRS symbols in eachfrequency-hop. In an example, additional DMRS using pre-DFT multiplexingof DMRS and data may be used. In an example, two DMRS symbol perfrequency-hop may be used when the payload size is less than Y and eachfrequency-hop with less than or equal to X=6 number of symbols.Otherwise, one DMRS symbol per frequency-hop may be used. In an example,for long PUCCH over multiple slots, the duration(s) of long PUCCH ineach slot may be the same or may be different. In an example, forslot-based scheduling, HARQ feedback with more than 2 bits, PUSCH may berate-matched. In an example, for slot-based scheduling, for HARQfeedback with up to two bits, PUSCH may be punctured. In an example, forUCI on PUSCH, β_(offset) may be dynamically or semi-staticallyconfigured. In an example, a set of PUCCH resources at least for HARQfeedback may be configured to a wireless device by higher layersignaling. In an example, one or multiple set(s) of PUCCH resourcesconsisting of same or different PUCCH formats may be configured. In anexample, one or multiple set(s) of PUCCH resources for each PUCCH formatmay be configured. In an example, a set of PUCCH resources for eachduration of each PUCCH format may be configured. In an example, a set ofPUCCH resources for PUCCH formats carrying up to 2 bits UCI may beconfigured. In an example, another set of PUCCH resources for PUCCHformats carrying more 2 bits UCI may be configured.

In an example, for open-loop power control parameters for a PUSCH, gNBmay configure one or more multiple P0 values. For example, for specificcombination(s) of one or more beam(s), waveform and/or service type maybe configured. In an example, gNB may configure one or multiple alphavalues. In an example, path loss calculation may be based on periodicCSI-RS if configured. In an example, path loss calculation may be basedon periodic CSI-RS for example for power calculation of PUSCH and/or SRSand/or PUCCH. In an example, both SSS and DM-RS for PBCH of SS block maybe used for PL calculation of UL power control if the power offsetbetween SSS and DM-RS for PBCH is known by the wireless device. In anexample, if the power offset between SSS and DM-RS for PBCH is not knownby the wireless device, SSS of SS block may be used for path losscomputation for uplink power control. In an example, CSI-RS may be usedfor path loss computation of uplink power control. In an example, two ormore downlink reference signals may be used and the path lossmeasurements may be combined.

Example power control mechanism is described here. Some detailedparameters are provided in examples. The basic processes may beimplemented in technologies such as LTE, New Radio, and/or othertechnologies. A radio technology may have its own specific parameters.Example embodiments describe a method for implementing power controlmechanism. Other example embodiments of the invention using differentparameters may be implemented. Some example embodiments enhance physicallayer power control mechanisms when a plurality of PUCCHs aretransmitted in parallel.

In an example embodiment, downlink power control may determine theEnergy Per Resource Element (EPRE). The term resource element energy maydenote the energy prior to CP insertion. The term resource elementenergy may denote the average energy taken over all constellation pointsfor the modulation scheme applied. Uplink power control determines theaverage power over a SC-FDMA symbol in which the physical channel may betransmitted.

In an example, plink power control may control the transmit power of thedifferent uplink physical channels.

In an example, if a UE is configured with a LAA SCell for uplinktransmissions, the UE may apply the procedures described for PUSCH andSRS in this clause assuming frame structure type 1 for the LAA SCellunless stated otherwise.

In an example, for PUSCH, the transmit power {circumflex over(P)}_(PUSCH,c)(i), may be first scaled by the ratio of the number ofantennas ports with a non-zero PUSCH transmission to the number ofconfigured antenna ports for the transmission scheme. The resultingscaled power may be then split equally across the antenna ports on whichthe non-zero PUSCH is transmitted. For PUCCH or SRS, the transmit power{circumflex over (P)}_(PUCCH)(i), or {circumflex over (P)}_(SRS,c)(i)may be split equally across the configured antenna ports for PUCCH orSRS. In an example, {circumflex over (P)}_(SRS,c)(i) may be the linearvalue of P_(SRS,c)(i). A cell wide overload indicator (OI) and a HighInterference Indicator (HII) to control UL interference may beparameters in LTE or 5G technology.

In an example, if the UE is configured with a SCG, the UE may apply theprocedures described in this clause for both MCG and SCG. In an example,when the procedures are applied for MCG, the terms ‘secondary cell’,‘secondary cells’, ‘serving cell’, ‘serving cells’ in this clause referto secondary cell, secondary cells, serving cell, serving cellsbelonging to the MCG respectively. In an example, when the proceduresare applied for SCG, the terms ‘secondary cell’, ‘secondary cells’,‘serving cell’, ‘serving cells’ in this clause refer to secondary cell,secondary cells (not including PSCell), serving cell, serving cellsbelonging to the SCG respectively. The term ‘primary cell’ in thisclause refers to the PSCell of the SCG.

In an example, if the UE is configured with a PUCCH-SCell, the UE mayapply the procedures described in this clause for both primary PUCCHgroup and secondary PUCCH group. In an example, when the procedures areapplied for primary PUCCH group, the terms ‘secondary cell’, ‘secondarycells’, ‘serving cell’, ‘serving cells’ in this clause refer tosecondary cell, secondary cells, serving cell, serving cells belongingto the primary PUCCH group respectively. In an example, when theprocedures are applied for secondary PUCCH group, the terms ‘secondarycell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ in this clauserefer to secondary cell, secondary cells, serving cell, serving cellsbelonging to the secondary PUCCH group respectively.

In an example, if the UE transmits PUSCH without a simultaneous PUCCHfor the serving cell c, then the UE transmit power P_(PUSCH,c)(i) forPUSCH transmission in subframe i for the serving cell C may be given by

$\begin{matrix}{{P_{{PUSCH},c}(i)} = {\min{\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\\begin{matrix}{{10{\log_{10}( {M_{PUSCH,c}(i)} )}} + {P_{O_{-}PUSCH,c}(j)} +} \\{{{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{TF,c}(i)} + {f_{c}(i)}}\end{matrix}\end{Bmatrix}\lbrack {{dB}\; m} \rbrack}}} & \;\end{matrix}$

In an example, if the UE transmits PUSCH simultaneous with PUCCH for theserving cell c, then the UE transmit power P_(PUSCH,c)(i) for the PUSCHtransmission in subframe i for the serving cell c may be given by

$\begin{matrix}{{P_{{PUSCH},c}(i)} = {\min{\begin{Bmatrix}{{10{\log_{10}( {{{\hat{P}}_{{CMAX},c}(i)} - {{\hat{P}}_{PUCCH}(i)}} )}},} \\\begin{matrix}{{10{\log_{10}( {M_{PUSCH,c}(i)} )}} + {P_{O_{-}PUSCH,c}(j)} +} \\{{{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{TF,c}(i)} + {f_{c}(i)}}\end{matrix}\end{Bmatrix}\lbrack {{dB}\; m} \rbrack}}} & \;\end{matrix}$

In an example, if the UE is not transmitting PUSCH for the serving cellc, for the accumulation of TPC command received with DCI format 3/3A forPUSCH, the UE may assume that the UE transmit power P_(PUSCH,c)(i) forthe PUSCH transmission in subframe i for the serving cell c is computedbyP _(PUSCH,c)(i)=min{P _(CMAX,c)(i),P _(O_PUSCH,c)(1)+α_(c)(1)·PL_(c) +f_(c)(i)} [dBm]

In an example, P_(CMAX,c)(i) is the configured UE transmit power insubframe i for serving cell c and P_(CMAX,c)(i) is the linear value ofP_(CMAX,c)(i). In an example, if the UE transmits PUCCH without PUSCH insubframe i for the serving cell c, the accumulation of TPC commandreceived with DCI format 3/3A for PUSCH may be considered. In anexample, if the UE does not transmit PUCCH and PUSCH in subframe i forthe serving cell c, for the accumulation of TPC command received withDCI format 3/3A for PUSCH, the UE shall compute P_(CMAX,c)(i) assumingMPR=0 dB, A-MPR=0 dB, P-MPR=0 dB and □TC=0 dB. In an example,{circumflex over (P)}_(PUCCH)(i) may be the linear value ofP_(PUCCH)(i). In an example, M_(PUSCH,c)(i) is the bandwidth of thePUSCH resource assignment expressed in number of resource blocks validfor subframe i and serving cell c. In an example, the UE may beconfigured with higher layer parameter UplinkPowerControlDedicated-v12x0for serving cell c. In an example, subframe i may belong to uplink powercontrol subframe set 2 as indicated by the higher layer parametertpc-SubframeSet-r12.

In an example, when j=0,P _(O_PUSCH,c)(0)=P _(O_UE_PUSCH,c,2)(0)+P _(O_NOMINAL_PUSCH,c,2)(0),where j=0 is used for PUSCH (re)transmissions corresponding to asemi-persistent grant, P_(O_UE_PUSCH,c,2)(0) andP_(O_NOMINAL_PUSCH,c,2)(0) are the parametersp0-UE-PUSCH-Persistent-SubframeSet2-r12 andp0-NominalPUSCH-Persistent-SubframeSet2-r12 respectively provided byhigher layers, for each serving cell c.

In an example, when j=1,P _(O_PUSCH,c)(1)=P _(O_UE_PUSCH,c,2)(1)+P _(O_NOMINAL_PUSCH,c,2)  (1)where j=1 is used for PUSCH (re)transmissions corresponding to a dynamicscheduled grant. P_(O_UE_PUSCH,c,2) (1) and P_(O_NOMINAL_PUSCH,c,2)(1)are the parameters p0-UE-PUSCH-SubframeSet2-r12 andp0-NominalPUSCH-SubframeSet2-r12 respectively, provided by higher layersfor serving cell c.

In an example, when j=2,P _(O_PUSCH,c)(2)=P _(O_UE_PUSCH,c)(2)+P _(O_NOMINAL_PUSCH,c)  (2)where P_(O_UE_PUSCH,c) (2)=0 andP_(O_NOMINAL_PUSCH,c)(2)=P_(O_PRE)+Δ_(PREAMBLE_Msg3), where theparameter preambleInitialReceivedTargetPower (P_(O_PRE)) andΔ_(PREAMBLE_Msg3) are signalled from higher layers for serving cell c,where j=2 is used for PUSCH (re)transmissions corresponding to therandom access response grant.

In an example, P_(O_PUSCH,c)(j) is a parameter composed of the sum of acomponent P_(O_NOMINAL_PUSCH,c) (j) provided from higher layers for j=0and 1 and a component P_(O_UE_PUSCH,c) (j) provided by higher layers forj=0 and 1 for serving cell c. For PUSCH (re)transmissions correspondingto a semi-persistent grant then j=0, for PUSCH (re)transmissionscorresponding to a dynamic scheduled grant then j=1 and for PUSCH(re)transmissions corresponding to the random access response grant thenj=2. P_(O_UE_PUSCH,c) (2)=0 and P_(O_NOMINAL_PUSCH,c)(2)=P_(O_PRE)+Δ_(PREAMBLE_Msg3), where the parameterpreambleInitialReceivedTargetPower (P_(O_PRE)) and Δ_(PREAMBLE_Msg3) aresignalled from higher layers for serving cell c.

In an example, if the UE is configured with higher layer parameterUplinkPowerControlDedicated-v12x0 for serving cell c and if subframe ibelongs to uplink power control subframe set 2 as indicated by thehigher layer parameter tpc-SubframeSet-r12, For j=0 or 1,α_(c)(j)=α_(c,2)∈{0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1}. α_(c,2) may bethe parameter alpha-SubframeSet2-r12 provided by higher layers for eachserving cell c. For j=2, α_(c)(j)=1. Otherwise, for j=0 or 1, α_(c)∈{0,0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1} may be a 3-bit parameter provided byhigher layers for serving cell c. In an example, for j=2, α_(c)(j)=1.

In an example, PL_(c) may be the downlink path loss estimate calculatedin the UE for serving cell c in dB andPL_(c)=referenceSignalPower−higher layer filtered RSRP, wherereferenceSignalPower may be provided by higher layers and RSRP may bedefined for the reference serving cell and the higher layer filterconfiguration may be defined for the reference serving cell.

In an example, if serving cell c belongs to a TAG containing the primarycell then, for the uplink of the primary cell, the primary cell may beused as the reference serving cell for determining referenceSignalPowerand higher layer filtered RSRP. For the uplink of the secondary cell,the serving cell configured by the higher layer parameterpathlossReferenceLinking may be used as the reference serving cell fordetermining referenceSignalPower and higher layer filtered RSRP.

In an example, if serving cell c belongs to a TAG containing the PSCellthen, for the uplink of the PSCell, the PSCell may be used as thereference serving cell for determining referenceSignalPower and higherlayer filtered RSRP; for the uplink of the secondary cell other thanPSCell, the serving cell configured by the higher layer parameterpathlossReferenceLinking may be used as the reference serving cell fordetermining referenceSignalPower and higher layer filtered RSRP.

In an example, if serving cell c belongs to a TAG not containing theprimary cell or PSCell then serving cell c is used as the referenceserving cell for determining referenceSignalPower and higher layerfiltered RSRP.

In an example, Δ_(TF,c)(i)=10 log₁₀ ((2^(BPRE·K) ^(S) −1)·β_(offset)^(PUSCH)) for K_(S)=1.25 and 0 for K_(S)=0 where K_(S) may be given bythe parameter deltaMCS-Enabled provided by higher layers for eachserving cell c. In an example, BPRE and β_(offset) ^(PUSCH), for eachserving cell c, may be computed as below. In an example, K_(S)=0 fortransmission mode 2.

In an example, BPRE=O_(CQI)/N_(RE) for control data sent via PUSCHwithout UL-SCH data and Σ_(r=0) ^(c-1) K_(r)/N_(RE) for other cases. Inan example, C may be the number of code blocks, K_(r) may be the sizefor code block r, O_(CQI) may be the number of CQI/PMI bits includingCRC bits and N_(RE) may be the number of resource elements determined asN_(RE)=M_(sc) ^(PUSCH-initial), N_(symb) ^(PUSCH-initial), where C,K_(r), M_(sc) ^(PUSCH-initial) and N_(symb) ^(PUSCH-initial) areparameters in LTE technology. In an example, β_(offset)^(PUSCH)=β_(offset) ^(CQI) for control data sent via PUSCH withoutUL-SCH data and one for other cases.

In an example, δ_(PUSCH,c) may be a correction value, also referred toas a TPC command and may be included in PDCCH/EPDCCH with DCI format0/0A/0B/4/4A/4B or in MPDCCH with DCI format 6-0A for serving cell c orjointly coded with other TPC commands in PDCCH/MPDCCH with DCI format3/3A whose CRC parity bits are scrambled with TPC-PUSCH-RNTI. If the UEis configured with higher layer parameterUplinkPowerControlDedicated-v12x0 for serving cell c and if subframe ibelongs to uplink power control subframe set 2 as indicated by thehigher layer parameter tpc-SubframeSet-r12, the current PUSCH powercontrol adjustment state for serving cell c may be given by f_(c,2)(i),and the UE may use f_(c,2)(i) instead of f_(c)(i) to determineP_(PUSCH,c)(i). Otherwise, the current PUSCH power control adjustmentstate for serving cell c may be given by f_(c)(i). f_(c,2)(i) andf_(c)(i) may be defined by: f_(c)(i)=f_(c)(i−1)+δ_(PUSCH,c)(i−K_(PUSCH))and f_(c,2)(i)=f_(c,2)(i−1)+δ_(PUSCH,c)(i−K_(PUSCH)) if accumulation isenabled based on the parameter Accumulation-enabled provided by higherlayers or if the TPC command δ_(PUSCH,c) is included in a PDCCH/EPDCCHwith DCI format 0 or in a MPDCCH with DCI format 6-0A for serving cell cwhere the CRC is scrambled by the Temporary C-RNTI. In an example,δ_(PUSCH,c)(i−K_(PUSCH)) was signalled on PDCCH/EPDCCH with DCI format0/0A/0B/4/4A/4B or MPDCCH with DCI format 6-0A or PDCCH/MPDCCH with DCIformat 3/3A on subframe i−K_(PUSCH,) and where f_(c)(0) is the firstvalue after reset of accumulation. For a BL/CE UE configured withCEModeA, subframe i−K_(PUSCH) may be the last subframe in which theMPDCCH with DCI format 6-0A or MPDCCH with DCI format 3/3A istransmitted.

In an example, for FDD or FDD-TDD and serving cell frame structure type1, K_(PUSCH)=4. In an example, for TDD, if the UE is configured withmore than one serving cell and the TDD UL/DL configuration of at leasttwo configured serving cells is not the same, or if the UE is configuredwith the parameter EIMTA-MainConfigServCell-r12 for at least one servingcell, or for FDD-TDD and serving cell frame structure type 2, the “TDDUL/DL configuration” may refer to the UL-reference UL/DL configurationfor serving cell c. In an example, for TDD UL/DL configurations 1-6 andUE not configured with higher layer parameter symPUSCH-UpPts-r14 for theserving cell c, K_(PUSCH) may be specified. In an example, for TDD UL/DLconfiguration 0 and UE not configured with higher layer parametersymPUSCH-UpPts-r14 for the serving cell c. In an example, if the PUSCHtransmission in subframe 2 or 7 is scheduled with a PDCCH/EPDCCH of DCIformat 0/4 or a MPDCCH with DCI format 6-0A in which the LSB of the ULindex is set to 1, K_(PUSCH)=7. In an example, For all other PUSCHtransmissions, K_(PUSCH) may be specified. In an example, for TDD UL/DLconfigurations 0-5 and UE configured with higher layer parametersymPUSCH-UpPts-r14 for the serving cell c, K_(PUSCH) may be specified.In an example, for TDD UL/DL configuration 6 and UE configured withhigher layer parameter symPUSCH-UpPts-r14 for the serving cell c, if thePUSCH transmission in subframe 2 or 7 is scheduled with a PDCCH/EPDCCHof DCI format 0/4 in which the LSB of the UL index is set to 1,K_(PUSCH)=6 and for all other PUSCH transmissions, K_(PUSCH) may bespecified.

In an example, the δ_(PUSCH,c) dB absolute values signalled onPDCCH/EPDCCH with DCI format 0/0A/0B/4/4A/4B or a MPDCCH with DCI format6-0A may be given in Table 2. If the PDCCH/EPDCCH with DCI format 0 or aMPDCCH with DCI format 6-0A is validated as a SPS activation or releasePDCCH/EPDCCH/MPDCCH, then δ_(PUSCH,c) may be 0 dB.

In an example, for a non-BL/CE UE, f_(c)(i)=f_(c)(i−1) andf_(c,2)(i)=f_(c,2)(i−1) for a subframe where no PDCCH/EPDCCH with DCIformat 0/0A/0B/4/4A/4B is decoded for serving cell c or where DRX occursor i is not an uplink subframe in TDD or FDD-TDD and serving cell cframe structure type 2.

In an example, for a BL/CE UE configured with CEModeA,f_(c)(i)=f_(c)(i−1) and f_(c,2)(i)=f_(c,2)(i−1) for a subframe where noMPDCCH with DCI format 6-0A is decoded for serving cell c or where DRXoccurs or i is not an uplink subframe in TDD.

In an example, if the UE is configured with higher layer parameterUplinkPowerControlDedicated-v12x0 for serving cell c and if subframe ibelongs to uplink power control subframe set 2 as indicated by thehigher layer parameter tpc-SubframeSet-r12. If subframe i does notbelong to uplink power control subframe set 2 as indicated by the higherlayer parameter tpc-SubframeSet-r12 f_(c,2)(i)=f_(c,2)(i−1).

In an example, for both types of f_(c) (*) (accumulation or currentabsolute) the first value is set as follows: If P_(O_UE_PUSCH,c) valueis changed by higher layers and serving cell c is the primary cell or,if P_(O_UE_PUSCH,c) value is received by higher layers and serving cellc is a Secondary cell, f_(c) (0)=0. Otherwise, If the UE receives therandom access response message for a serving cell c,f_(c)(0)=ΔP_(rampupc)+δ_(msg2,c), where δ_(msg2,c) is the TPC commandindicated in the random access response corresponding to the randomaccess preamble transmitted in the serving cell c, and

$\begin{matrix}{{\Delta P_{{rampup},c}} = {\min\lbrack {\{ {\max( {0,{P_{{C{MAX}},c} - \ \begin{pmatrix}{{10\;{\log_{10}( {M_{{PUSH},c}(0)} )}} +} \\{{P_{{O_{-}P{USCH}},c}(2)} + \delta_{{msg}\; 2} +} \\{{{\alpha_{c}(2)} \cdot {PL}} + {\Delta_{{TF},c}(0)}}\end{pmatrix}}} )} \},{\Delta P_{{rampuprequested},c}}} \rbrack}} & \;\end{matrix}$and ΔP_(rampuprequested,c) is provided by higher layers and correspondsto the total power ramp-up requested by higher layers from the first tothe last preamble in the serving cell c, M_(PUSCH,c)(0) is the bandwidthof the PUSCH resource assignment expressed in number of resource blocksvalid for the subframe of first PUSCH transmission in the serving cellc, and ΔTF,c(0) is the power adjustment of first PUSCH transmission inthe serving cell c. In an example, If P_(O_UE_PUSCH,c,2) value isreceived by higher layers for a serving cell c, f_(c,2)(0)=0.

In an example, if the UE is not configured with an SCG or a PUCCH-SCell,and if the total transmit power of the UE would exceed {circumflex over(P)}_(CMAX)(i), the UE may scale {circumflex over (P)}_(PUSCH,c)(i) forthe serving cell c in subframe i such that the condition

$\begin{matrix}{{\sum\limits_{c}{{w(i)} \cdot {{\overset{\hat{}}{P}}_{{PU{SCH}},c}(i)}}} \leq ( {{{\overset{\hat{}}{P}}_{CMAX}(i)} - {{\overset{\hat{}}{P}}_{PUCCH}(i)}} )} & \;\end{matrix}$is satisfied where {circumflex over (P)}_(PUCCH)(i) may be the linearvalue of P_(PUCCH)(i), {circumflex over (P)}_(PUSCH,c)(i) may be thelinear value of P_(PUSCH,c)(i), {circumflex over (P)}_(CMAX)(i) may bethe linear value of the UE total configured maximum output powerP_(CMAX) in subframe i and w(i) may be a scaling factor of {circumflexover (P)}_(PUSCH,c)(i) for serving cell c where 0≤w(i)≤1. In case thereis no PUCCH transmission in subframe i, {circumflex over(P)}_(PUCCH)(i)=0.

In an example, if the UE is not configured with an SCG or a PUCCH-SCell,and if the UE has PUSCH transmission with UCI on serving cell j andPUSCH without UCI in any of the remaining serving cells, and the totaltransmit power of the UE would exceed {circumflex over (P)}_(CMAX)(i),the UE may scale {circumflex over (P)}_(PUSCH,c)(i) for the servingcells without UCI in subframe i such that the condition

$\begin{matrix}{{\sum\limits_{c \neq j}{{w(i)} \cdot {{\overset{\hat{}}{P}}_{{PUSCH},c}(i)}}} \leq ( {{{\overset{\hat{}}{P}}_{CMAX}(i)}\  - {{\overset{\hat{}}{P}}_{{PUSCH},j}(i)}} )} & \;\end{matrix}$is satisfied where {circumflex over (P)}_(PUSCH)(i) is the PUSCHtransmit power for the cell with UCI and w(i) is a scaling factor of{circumflex over (P)}_(PUSCH,c)(i) for serving cell c without UCI. Inthis case, no power scaling may be applied to {circumflex over(P)}_(PUSCH,j)(i) unless

$\begin{matrix}{{\sum\limits_{c \neq j}{{w(i)} \cdot {{\overset{\hat{}}{P}}_{{PUSCH},c}(i)}}} = 0} & \;\end{matrix}$and the total transmit power of the UE still would exceed {circumflexover (P)}_(CMAX)(i).

In an example, for a UE not configured with a SCG or a PUCCH-SCell, w(i)values may be the same across serving cells when w(i)>0 but for certainserving cells w(i) may be zero.

In an example, if the UE is not configured with an SCG or a PUCCH-SCell,and if the UE has simultaneous PUCCH and PUSCH transmission with UCI onserving cell j and PUSCH transmission without UCI in any of theremaining serving cells, and the total transmit power of the UE wouldexceed {circumflex over (P)}_(CMAX)(i), the UE may obtain {circumflexover (P)}_(PUSCH,c)(i) according to

$\begin{matrix}{{{{\overset{\hat{}}{P}}_{{P{USCH}},j}(i)} = {{\min( {{{\overset{\hat{}}{P}}_{{P{USCH}},j}(i)},( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{PUCCH}(i)}} )} )}\mspace{14mu}{and}}}{{\sum\limits_{c \neq j}{{w(i)} \cdot {{\overset{\hat{}}{P}}_{{PUSCH},c}(i)}}} \leq ( {{{\overset{\hat{}}{P}}_{CMAX}(i)}\  - {{\overset{\hat{}}{P}}_{PUCCH}(i)}\  - {{\overset{\hat{}}{P}}_{{PUSCH},j}(i)}} )}} & \;\end{matrix}$

In an example, if the UE is not configured with a SCG or a PUCCH-SCell,and If the UE is configured with multiple TAGs, and if the PUCCH/PUSCHtransmission of the UE on subframe i for a given serving cell in a TAGoverlaps some portion of the first symbol of the PUSCH transmission onsubframe i+1 for a different serving cell in another TAG the UE mayadjust its total transmission power to not exceed P_(CMAX) on anyoverlapped portion.

In an example, if the UE is not configured with a SCG or a PUCCH-SCelland if the UE is configured with multiple TAGs, and if the PUSCHtransmission of the UE on subframe i for a given serving cell in a TAGoverlaps some portion of the first symbol of the PUCCH transmission onsubframe i+1 for a different serving cell in another TAG the UE mayadjust its total transmission power to not exceed P_(CMAX) on anyoverlapped portion.

In an example, if the UE is not configured with a SCG or a PUCCH-SCelland if the UE is configured with multiple TAGs, and if the SRStransmission of the UE in a symbol on subframe i for a given servingcell in a TAG overlaps with the PUCCH/PUSCH transmission on subframe forsubframe i+1 for a different serving cell in the same or another TAG theUE may drop SRS if its total transmission power exceeds P_(CMAX) on anyoverlapped portion of the symbol.

In an example, if the UE is not configured with a SCG or a PUCCH-SCelland if the UE is configured with multiple TAGs and more than 2 servingcells, and if the SRS transmission of the UE in a symbol on subframe ifor a given serving cell overlaps with the SRS transmission on subframei for a different serving cell(s) and with PUSCH/PUCCH transmission onsubframe i or subframe i+1 for another serving cell(s) the UE may dropthe SRS transmissions if the total transmission power exceeds P_(CMAX)on any overlapped portion of the symbol.

In an example, if the UE is not configured with a SCG or a PUCCH-SCelland if the UE is configured with multiple TAGs, the UE may, whenrequested by higher layers, to transmit PRACH in a secondary servingcell in parallel with SRS transmission in a symbol on a subframe of adifferent serving cell belonging to a different TAG, drop SRS if thetotal transmission power exceeds P_(CMAX) on any overlapped portion inthe symbol.

In an example, if the UE is not configured with a SCG or a PUCCH-SCelland if the UE is configured with multiple TAGs, the UE may, whenrequested by higher layers, to transmit PRACH in a secondary servingcell in parallel with PUSCH/PUCCH in a different serving cell belongingto a different TAG, adjust the transmission power of PUSCH/PUCCH so thatits total transmission power does not exceed P_(CMAX) on the overlappedportion.

In an example, if the UE is configured with a LAA SCell for uplinktransmissions, the UE may compute the scaling factor w(i) assuming thatthe UE performs a PUSCH transmission on the LAA SCell in subframe iirrespective of whether the UE can access the LAA SCell for the PUSCHtransmission in subframe i according to the channel access procedures.

In an example, for a BL/CE UE configured with CEModeA, if the PUSCH istransmitted in more than one subframe i0, i1, . . . , iN−1 where i0<i1<. . . <iN−1, the PUSCH transmit power in subframe ik, k=0, 1, . . . ,N−1, may be determined by P_(PUSCH,c)(i_(k))=P_(PUSCH,c)(i₀). For aBL/CE UE configured with CEModeB, the PUSCH transmit power in subframeik may be determined by P_(PUSCH,c)(i_(k))=P_(CMAX,c)(i₀).

In an example, if serving cell c is the primary cell, for PUCCH format1/1a/1b/2/2a/2b/3, the setting of the UE Transmit power P_(PUCCH) forthe physical uplink control channel (PUCCH) transmission in subframe ifor serving cell c may be defined by

$\begin{matrix}{{P_{PUCCH}(i)} = {\min{\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\\begin{matrix}{P_{0{\_{PUCCH}}} + {PL_{c}} + {h( {n_{CQI},n_{HARQ},n_{SR}} )} +} \\{{\Delta_{F\_{PUCCH}}(F)} + {\Delta_{TxD}( F^{\prime} )} + {g(i)}}\end{matrix}\end{Bmatrix}\lbrack {{dB}\; m} \rbrack}}} & \;\end{matrix}$

In an example, if the UE is not transmitting PUCCH for the primary cell,for the accumulation of TPC command for PUCCH, the UE may assume thatthe UE transmit power P_(PUCCH) for PUCCH in subframe i may be computedbyP _(PUCCH)(i)=min{P _(CMAX,c)(i),P _(0_PUCCH)+PL_(c) +g(i)} [dBm]

In an example, P_(CMAX,c)(i) may be the configured UE transmit power insubframe i for serving cell c. If the UE transmits PUSCH without PUCCHin subframe i for the serving cell c, for the accumulation of TPCcommand for PUCCH, the UE may assume P_(CMAX,c)(i) as given by LTEprocedures. If the UE does not transmit PUCCH and PUSCH in subframe ifor the serving cell c, for the accumulation of TPC command for PUCCH,the UE may compute P_(CMAX,c)(i) assuming MPR=0 dB, A-MPR=0 dB, P-MPR=0dB and □TC=0 dB, where MPR, A-MPR, P-MPR and □TC are LTE parameters.

In an example, the parameter Δ_(F_PUCCH)(F) may be provided by higherlayers. Each Δ_(F_PUCCH)(F) value may correspond to a PUCCH format (F)relative to PUCCH format 1a, where each PUCCH format (F).

In an example, if the UE is configured by higher layers to transmitPUCCH on two antenna ports, the value of Δ_(T×D)(F′) may be provided byhigher layers where each PUCCH format F′ is defined according to LTEprocedures. otherwise, Δ_(T×D)(F′)=0.

In an example, h(n_(CQI), n_(HARQ), n_(SR)) may be a PUCCH formatdependent value, where n_(CQI) may correspond to the number ofinformation bits for the channel quality information. n_(SR)=1 ifsubframe i is configured for SR for the UE not having any associatedtransport block for UL-SCH, otherwise n_(SR)=0. If the UE is configuredwith more than one serving cell, or the UE is configured with oneserving cell and transmitting using PUCCH format 3, the value ofn_(HARQ) is defined according to LTE procedures; otherwise, n_(HARQ) maybe the number of HARQ-ACK bits sent in subframe i. In an example, forPUCCH format 1,1a and 1b h(n_(CQI), n_(HARQ), n_(SR))=0. In an example,for PUCCH format 1b with channel selection, if the UE is configured withmore than one serving cell,

${{h( {n_{CQI},n_{H{ARQ}},n_{SR}} )} = \frac{( {n_{HARQ} - 1} )}{2}},$otherwise, h(n_(CQI), n_(HARQ), n_(SR))=0. In an example, for PUCCHformat 2, 2a, 2b and normal cyclic prefix

${h( {n_{CQI},n_{HARQ},n_{SR}} )} = \{ \begin{matrix}{10{\log_{10}( \frac{n_{CQI}}{4} )}} & {{{if}\mspace{14mu} n_{CQI}}\  \geq 4} \\0 & {otherwise}\end{matrix} $

In an example, for PUCCH format 2 and extended cyclic prefix

${h( {n_{CQI},n_{HARQ},n_{SR}} )} = \{ \begin{matrix}{{10{\log_{10}( \frac{n_{CQI} + n_{HARQ}}{4} )}}\;} & {{{{if}\mspace{14mu} n_{CQI}} + n_{HARQ}} \geq 4} \\{0\ } & {otherwise}\end{matrix} $

In an example, for PUCCH format 3 and when UE transmits HARQ-ACK/SRwithout periodic CSI, if the UE is configured by higher layers totransmit PUCCH format 3 on two antenna ports, or if the UE transmitsmore than 11 bits of HARQ-ACK/SR

${h( {n_{CQI},n_{HARQ},n_{SR}} )} = \frac{n_{HARQ} + n_{SR} - 1}{3}$${otherwise},{{h( {n_{CQI},n_{HARQ},n_{SR}} )} = \frac{n_{HARQ} + n_{SR} - 1}{2}}$

In an example, for PUCCH format 3 and when UE transmits HARQ-ACK/SR andperiodic CSI, if the UE is configured by higher layers to transmit PUCCHformat 3 on two antenna ports, or if the UE transmits more than 11 bitsof HARQ-ACK/SR and CSI

${h( {n_{CQI},n_{H{ARQ}},n_{SR}} )} = \frac{n_{HARQ} + n_{SR} + n_{CQI} - 1}{3}$${otherwise},{{h( {n_{CQI},n_{H{ARQ}},n_{SR}} )} = \frac{n_{HARQ} + n_{SR} + n_{CQI} - 1}{2}}$

In an example, for PUCCH format 4, M_(PUCCH,c)(i) is the bandwidth ofthe PUCCH format 4 expressed in number of resource blocks valid forsubframe i and serving cell c. For PUCCH format 5, M_(PUCCH,c)(i)=1.

In an example embodiment, a wireless device may receive one or moremessages. The one or more messages may comprise one or more RRCmessages. The one or more RRC messages may comprise configurationparameters for one or more cells. In an example, the one or more cellsmay comprise a primary cell. In an example, the one or more cells maycomprise a primary cell and one or more secondary cells. In an example,the one or more messages may comprise configuration parameters for oneor more logical channels. In an example, a logical channel maycorrespond to a service type (e.g., eMBB, URLLC, mMTC, etc.). In anexample, there may be mapping between logical channel/service type to aTTI/numerology. In an example, the one or more RRC messages may compriseconfiguration parameters for one or more physical uplink controlchannels (PUCCHs). In an example, the one or more PUCCHs may compriseone or more long PUCCHs and/or one or more short PUCCHs. A short PUCCHand a long PUCCH may carry different number of UCI and/or may havedifferent capacity (e.g., in terms of number of bits). In an example, aPUCCH in the one or more PUCCH may correspond to a service type/logicalchannel/TTI/numerology. In an example, the one or more short PUCCHs maycomprise short PUCCH(s) with different durations in time domain. In anexample, the one or more short PUCCHs may comprise one or moretwo-symbol PUCCHs and/or one or more one-symbol PUCCHs. A one-symbolPUCCH may span one symbol in time domain. A two-symbol PUCCH may spantwo symbols in time domain. In an example, the wireless device maycalculate transmission powers for a plurality of signals. The pluralityof signals may be for transmission in a same first slot/subframe/TTI andon a same cell. The plurality signals may comprise one or more PUCCHand/or one or more PUSCH and/or one or more SRS, etc. In an example, theplurality of signals may have overlap in time domain. In an example, theplurality of signals may be multiplexed in frequency domain, e.g., mayoccupy different parts in the frequency domain and may have overlap inthe time domain. In an example, the plurality of signals may comprise afirst PUCCH and a second PUCCH. In an example, the first PUCCH and thesecond PUCCH may be multiplexed in time domain (e.g., TDMed). In anexample, the first PUCCH and the second PUCCH may be multiplexed infrequency domain (e.g., FDMed). The first PUCCH and the second PUCCH mayhave overlap in the time domain. In an example, the first PUCCH and thesecond PUCCH and/or other signals may share a total transmission power(e.g., total transmission power for the cell). The wireless device maycalculate transmission power of the plurality of signals employing powercontrol algorithms. The power control algorithms may comprise open-looppower control algorithms and/or closed-loop power control algorithms.The base station may transmit one or more commands (e.g., using one ormore DCI) and the wireless device may employ the one or more commands tocalculate transmission power levels for the plurality of signals. In anexample, the wireless device may be power-limited, e.g., the totalcalculated power for transmission of the plurality of signals may exceeda first limit. In an example, the first limit may be a maximumtransmission power per cell. In an example, the wireless device may bepower limited if the wireless device is located in the cell edge. In anexample, the wireless device may scale calculated power level(s) of oneor more signals in the plurality of signals in response to the wirelessdevice being power-limited. In an example, the wireless device may scalethe calculated power level(s) of one or more signals in the plurality ofsignals based on priorities associated with the plurality of signals. Inan example, the wireless device may drop one or more first signals inthe plurality of signals in response to the wireless device being powerlimited and the one or more signals having lower priority compared toother signals in the plurality of signals. An example scenario is shownin FIG. 15 . The wireless device may transmit one or more signals of theplurality of signals with their calculated/scaled transmission powerlevel in the first slot/subframe/TTI. In an example embodiment, inresponse to the wireless device being power limited, the wireless devicemay consider higher priority for the first PUCCH compared to the secondPUCCH.

In a new radio (NR) wireless system, a plurality of PUCCHs may bemultiplexed (e.g., frequency domain multiplexed) and may be transmittedin parallel. Legacy power control algorithms may not consider prioritiesassociated with a plurality of PUCCHs for power scaling of the pluralityof PUCCHs. The uplink control information (UCI) need to be transmittedwith high reliability. Legacy power control processes may lead toinefficient transmission of UCI and may lead to inefficient systemoperation. Example embodiment enhance the power control process in NR.Example embodiments may be combined to further enhance the power controlprocess, for example, in response to wireless device being power-limitedand the wireless device transmits a plurality of PUCCHs in parallel.

In an example embodiment, the first PUCCH may be a short PUCCH and thesecond PUCCH may be a long PUCCH. The wireless device may consider ahigher priority for the short PUCCH compared to the long PUCCH. Thewireless device may consider the higher priority of the short PUCCHcompared to the long PUCCH in power calculation of the short PUCCH andthe long PUCCH and/or scaling of the power of the short PUCCH and thelong PUCCH.

In an example embodiment, the first PUCCH may be a long PUCCH and thesecond PUCCH may be a short PUCCH. The wireless device may consider ahigher priority for the long PUCCH compared to the short PUCCH. Thewireless device may consider the higher priority of the long PUCCHcompared to the short PUCCH in power calculation of the short PUCCH andthe long PUCCH and/or scaling of the power of the short PUCCH and thelong PUCCH.

In an example embodiment, the first PUCCH may be a two-symbol shortPUCCH and the second PUCCH may be a one-symbol short PUCCH. The wirelessdevice may consider a higher priority for the two-symbol short PUCCHcompared to the one-symbol short PUCCH. The wireless device may considerthe higher priority of the two-symbol short PUCCH compared to theone-symbol short PUCCH in power calculation of the two-symbol shortPUCCH and the one-symbol short PUCCH and/or scaling of the power of thetwo-symbol short PUCCH and the one-symbol short PUCCH.

In an example embodiment, the first PUCCH may be a one-symbol shortPUCCH and the second PUCCH may be a two-symbol short PUCCH. The wirelessdevice may consider a higher priority for the one-symbol short PUCCHcompared to the short-symbol short PUCCH. The wireless device mayconsider the higher priority of the one-symbol short PUCCH compared tothe two-symbol short PUCCH in power calculation of the two-symbol shortPUCCH and the one-symbol short PUCCH and/or scaling of the power of thetwo-symbol short PUCCH and the one-symbol short PUCCH.

In an example embodiment, the first PUCCH may carry one or more firstUCI and the second PUCCH may carry one or more second UCI wherein thenumber of the one or more first UCI (e.g., first number of bitsassociated to the one or more first UCI) may be larger than the numberof the one or more second UCI (e.g., second number of bits associated tothe one or more second UCI). The wireless device may consider a higherpriority for the PUCCH that may carry larger number of one or more UCI(e.g., larger number of bits associated to the one or more UCI). Thewireless device may consider the higher priority of the first PUCCHcompared to the second PUCCH (e.g., higher priority for the PUCCH thatcarries larger number of one or more UCI and/or larger number of bitsassociated with one or more UCI) in power calculation of the first PUCCHand the second PUCCH and/or scaling of the power of the first PUCCH andthe second PUCCH.

In an example embodiment, the first PUCCH may be associated with and/ormay carry UCI corresponding to one or more first service types/logicalchannels/TTIs/numerologies. The second PUCCH may be associated withand/or may carry UCI corresponding to one or more second servicetypes/logical channels/TTIs/numerologies. In an example, the one or morefirst service types/logical channels/TTIs/numerologies may correspond toURLLC. In an example, the one or more second service types/logicalchannels/TTIs/numerologies may correspond to a non-URLLC service (e.g.,eMBB). The wireless device may consider the higher priority of the firstPUCCH compared to the second PUCCH (e.g., higher priority for the PUCCHthat corresponds to the one or more first service types/logicalchannels/TTIs/numerologies) in power calculation of the first PUCCH andthe second PUCCH and/or scaling of the power of the first PUCCH and thesecond PUCCH.

In an example embodiment, as shown in FIG. 16 and FIG. 17 , a wirelessdevice may receive one or more messages comprising configurationparameters. The one or more messages may comprise one or more RRCmessages. In an example, the one or more messages may compriseconfiguration parameters for a first uplink control channel and a seconduplink control channel. In an example, the one or more messages mayindicate a first resource (e.g., radio resource) for a first uplinkcontrol channel of a cell and a second resource (e.g., radio resource)for a second uplink control channel of the cell. In an example, thefirst resource may comprise a first plurality of time domain (e.g.,symbols) and frequency domain (e.g., RBs). In an example, the secondresource may comprise a second plurality of time domain (e.g., symbols)and frequency domain (e.g., RBs). In an example, the first radioresource and the second radio resource may overlap in one or more symboldurations.

In an example, the first uplink control channel may have a firstduration and the second uplink control channel may have a secondduration.

In an example, the first duration may be longer than the secondduration. In an example, the first priority may be higher than thesecond priority. In an example, the first duration may be longer thanthe second duration and the first priority may be higher that the secondpriority.

In an example, the first duration may be longer than the secondduration. In an example, the second priority may be higher than thefirst priority. In an example, the first duration may be longer than thesecond duration and the second priority may be higher than the firstpriority.

In an example, the first uplink control channel may carry a first numberof uplink control information and the second uplink control channel maycarry a second number of uplink control information. In an example, thefirst number is larger than the second number. In an example, the firstpriority is higher than the second priority. In an example, the firstnumber is larger than the second number and the first priority is higherthan the second priority.

In an example, the first uplink control channel corresponds to one ormore first logical channels and the second uplink control channelcorresponds to one or more second logical channels. In an example, thefirst priority may be higher than the second priority in response to theone or more first logical channels being corresponding to a firstservice type. In an example, the first service type may be ultrareliable low latency communications.

In an example, the first uplink control channel may correspond to one ormore first transmission durations and the second uplink control channelcorresponds to one or more second transmission durations. In an example,the first priority may be higher than the second priority in response toone or more first logical channels being mapped to the one or more firstdurations.

In an example, the wireless device may determine a plurality of powerlevels for a plurality of signals/channels (e.g., uplinksignals/channels). The plurality of power levels may comprise a firstpower level for transmission of one or more first uplink controlinformation via the first resource (e.g., by the first uplink controlchannel) and a second power level for transmission of one or more seconduplink control information via the second resource (e.g., by the seconduplink control channel).

In an example, the wireless device may receive one or more downlinkcontrol information indicating one or more parameters, wherein a firstpower level in the plurality of power levels is calculated based on theone or more parameters. In an example, a first power level in theplurality of power levels may be calculated based on an open loop powercontrol process. In an example, the first power level in the pluralityof power levels may be calculated based on a closed loop power controlprocess. In an example, a second power level in the plurality of powerlevels may be calculated based on a closed loop power control process.

In an example, the wireless device may determine that the wirelessdevice is power limited. In an example the wireless device may determinethat a sum of the plurality of power levels is larger than an allowedtransmission power. In an example, the wireless device may determinethat the wireless device is power limited in response to the sum of theplurality of power levels being larger than an allowed transmissionpower. In an example, the allowed transmission power may be a maximumwireless device transmission power. The wireless device may scale thefirst power level based on a first scaling factor, wherein the firstscaling factor is determined based on a first priority of the firstuplink control channel. In an example, the wireless device may scale thesecond power level based on a second scaling factor, wherein the secondscaling factor is determined based on a second priority of the seconduplink control channel. In an example, the wireless device may scale thefirst power level based on the first priority and/or the secondpriority. In an example, the wireless device may scale the second powerlevel based on the first priority and/or the second priority. In anexample, the wireless device may drop one or more signals in response tothe sum of the plurality of power levels being larger than the allowedtransmission power.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 18 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 1810, a wireless device may receive one ormore messages. The one or more messages may indicate a plurality ofresources comprising: a first resource for a first uplink controlchannel of a cell; and a second resource for a second uplink controlchannel of the cell. The first resource and the second resource mayoverlap in one or more symbol durations. At 1820, a plurality of powerlevels may be determined. The plurality of power levels may comprise: afirst power level for transmission of one or more first uplink controlinformation via the first resource; and a second power level fortransmission of one or more second uplink control information via thesecond resource. At 1830, the first power level may be scaled based on afirst scaling factor. The first scaling factor may be determined basedon a first priority of the first uplink control channel. At 1840, thesecond power level may be scaled based on a second scaling factor. Thesecond scaling factor may be determined based on a second priority ofthe second uplink control channel. A sum of the plurality of powerlevels may be larger than an allowed transmission power.

According to an example embodiment, the first uplink control channel mayhave a first duration and the second uplink control channel has a secondduration. According to an example embodiment: the first duration may belonger than the second duration; and the first priority may be higherthan the second priority. According to an example embodiment: the firstduration may be longer than the second duration; and the second prioritymay be higher than the first priority. According to an exampleembodiment, the first uplink control channel may carry a first number ofuplink control information and the second uplink control channel maycarry a second number of uplink control information. According to anexample embodiment, the first number may be larger than the secondnumber; and the first priority may be higher than the second priority.According to an example embodiment, the first uplink control channel maycorrespond to one or more first logical channels and the second uplinkcontrol channel may correspond to one or more second logical channels.According to an example embodiment, the first priority may be higherthan the second priority in response to the one or more first logicalchannels corresponding to a first service type. According to an exampleembodiment, the first service type may comprise ultra reliable lowlatency communications. According to an example embodiment, the firstuplink control channel may correspond to one or more first transmissiondurations and the second uplink control channel may correspond to one ormore second transmission durations. According to an example embodiment,the first priority may be higher than the second priority in response toone or more first logical channels being mapped to the one or more firstdurations. According to an example embodiment, the allowed transmissionduration may be a maximum wireless device transmission power. Accordingto an example embodiment, the first uplink control channel may have afirst duration and the second uplink control channel has a secondduration. According to an example embodiment, the first duration may belonger than the second duration; and the first priority may be higherthan the second priority. According to an example embodiment, the firstduration may be longer than the second duration; and the second prioritymay be higher than the first priority. According to an exampleembodiment, the first uplink control channel may carry a first number ofuplink control information and the second uplink control channel maycarry a second number of uplink control information. According to anexample embodiment, one or more downlink control information may bereceived. The one or more downlink control information may indicate oneor more parameters. A first power level in the plurality of power levelsmay be calculated based on the one or more parameters. According to anexample embodiment, a first power level in the plurality of power levelsmay be calculated based on an open loop power control process. Accordingto an example embodiment, a first power level in the plurality of powerlevels may be calculated based on a closed loop power control process.According to an example embodiment, one or more signals may be droppedin response to the sum of the plurality of power levels being largerthan the allowed transmission power.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using FDD communication systems. However, one skilled in the art willrecognize that embodiments of the invention may also be implemented in asystem comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 3-licensed assisted access). The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this invention may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. Only a limited number of example combinations areshown to indicate to one skilled in the art the possibility of featuresthat may be combined in various embodiments to create enhancedtransmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112, paragraph 6. Claims that do not expressly include the phrase“means for” or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, configuration parameters of: a first resource for a firstchannel, of a carrier, for transmitting first feedback; and a secondresource for a second channel of the carrier for transmitting secondfeedback, wherein the first resource and the second resource overlap inone or more symbol durations; determining power levels comprising: afirst power level for transmission of the first feedback via the firstresource; and a second power level for transmission of the secondfeedback via the second resource; in response to a sum of the powerlevels being larger than an allowed transmission power, dropping aconfigured transmission of the first feedback via the first resource,wherein the dropping is based on a first priority of the first channel;and transmitting the second feedback via the second resource.
 2. Themethod of claim 1, further comprising scaling the second power levelbased on a second scaling factor, wherein the second scaling factor isdetermined based on a second priority of the second channel.
 3. Themethod of claim 1, wherein at least one of the first feedback and thesecond feedback comprises at least one of: channel state information(CSI); positive acknowledgement (ACK); or negative acknowledgement(NACK).
 4. The method of claim 1, wherein the first channel has a firstduration and the second channel has a second duration.
 5. The method ofclaim 4, wherein: the first duration is longer than the second duration;and the first priority is higher than a second priority.
 6. The methodof claim 4, wherein: the first duration is longer than the secondduration; and a second priority is higher than the first priority. 7.The method of claim 1, wherein the first channel carries a first numberof uplink control information and the second channel carries a secondnumber of uplink control information.
 8. The method of claim 7, wherein:the first number is larger than the second number; and the firstpriority is higher than a second priority.
 9. The method of claim 1,wherein the first channel corresponds to one or more first logicalchannels and the second channel corresponds to one or more secondlogical channels.
 10. The method of claim 9, wherein the first priorityis higher than a second priority based on the one or more first logicalchannels corresponding to a first service type.
 11. The method of claim10, wherein the first service type is ultra reliable low latencycommunications.
 12. The method of claim 1, wherein the first channelcorresponds to one or more first transmission durations and the secondchannel corresponds to one or more second transmission durations. 13.The method of claim 12, wherein the first priority is higher than asecond priority based on one or more first logical channels being mappedto the one or more first transmission durations.
 14. The method of claim1, wherein the allowed transmission power is a maximum wireless devicetransmission power.
 15. The method of claim 14, wherein the firstchannel has a first duration and the second channel has a secondduration.
 16. The method of claim 15, wherein: the first duration islonger than the second duration; and the first priority is higher than asecond priority.
 17. The method of claim 15, wherein: the first durationis longer than the second duration; and a second priority is higher thanthe first priority.
 18. A non-transitory computer readable medium of awireless device having instructions stored thereon, the instructionsexecutable by one or more processors for: receiving, by a wirelessdevice, configuration parameters of: a first resource for a firstchannel, of a carrier, for transmitting first feedback; and a secondresource for a second channel of the carrier for transmitting secondfeedback, wherein the first resource and the second resource overlap inone or more symbol durations; determining power levels comprising: afirst power level for transmission of the first feedback via the firstresource; and a second power level for transmission of the secondfeedback via the second resource; in response to a sum of the powerlevels being larger than an allowed transmission power, dropping aconfigured transmission of the first feedback via the first resource,wherein the dropping is based on a first priority of the first channel;and transmitting the second feedback via the second resource.
 19. Thenon-transitory computer readable medium of claim 18, wherein theinstructions are further executable by one or more processors forscaling the second power level based on a second scaling factor, whereinthe second scaling factor is determined based on a second priority ofthe second channel.
 20. An apparatus for wireless communications,comprising: means for receiving configuration parameters of: a firstresource for a first channel, of a carrier, for transmitting firstfeedback; and a second resource for a second channel of the carrier fortransmitting second feedback, wherein the first resource and the secondresource overlap in one or more symbol durations; means for determiningpower levels comprising: a first power level for transmission of thefirst feedback via the first resource; and a second power level fortransmission of the second feedback via the second resource; means for,in response to a sum of the power levels being larger than an allowedtransmission power, dropping a configured transmission of the firstfeedback via the first resource, wherein the dropping is based on afirst priority of the first channel; and transmitting the secondfeedback via the second resource.